Site Menu.

My Desktop. :0.

Main Blog Page.
Site map.
Linux Information.
Image Browser.
Misc Doom Files.
Doom Wadfiles.
Yadex Editing Page.
CGI Code.
Perl Code.
Linux Configs.
My Linux System.
Console Cheats.
Misc Cheats.
PSX Doom Page.
Zdoom ACS.
The Shit List.
windows 3.0 Page.

Fun Flash game.

Misc American Images.

My .cshrc file. ~/.cshrc.

My .bashrc file. ~/.bashrc.

My .zshrc file. ~/.zshrc.

My Blackbox style file.
chernobyl.

Downloads.

These files are uuencoded because the tripod.com setup does not allow you to download files like *.bz2 and *.zip files. Since these are GNU/Linux files, I am encoding the files this way so they can be easily downloaded and uudecoded simply. It is best to create a new folder to save the files into so when you uudecode them you can easily find the files that are created.

My sysinfo program.
sys.txt.
Download this into a new directory & type uudecode sys.txt to undecode. This will give you sys.tar.bz2, then type tar -jxvf sys.tar.bz2.
Or here:http://one. fsphost.com/goten/sysinfo.kdevelop-1.0.tar.bz2.

Target Puzzle Solver. Solves the smh.com.au Sydney Morning Herald Target puzzle. Download this and type uudecode target.txt. This gives you target.c. Program written by Rod Johnson , November 6, 1995. I have hacked on this program to make it better and easier to use for a CGI script.

Configuration files.

My fvwm config file. This gives a Windows/Fvwm95 look with some very nice Window Decorations and a good color scheme. But without the ugly Windows wallpaper. That really does not look good.
~/.fvwm/.fvwm2rc.
Also needs this optional perl script in your $PATH.
~/bin/fvwm-desktop.

My .emacs file.
~/.emacs.

Xcdroast Tutorial.
Burning Ghost Images.

Linux Configurations.

Burning ISO images and Audio CDs.

If you want to do this using the command line then you can just put all of your files into a directory and arrange them as required, then use this command to create a ISO image of the files ready to write to a CD. Do not do this if you have files with spaces in the filenames. Rename them first. Then type: mkisofs -l -r -J -v -V "Music" -o music.iso Music/ to create a ISO image, Then you can use cdrecord to write the ISO file to a CD. Below is the result of running the cdrecord -scanbus dev=/dev/hdc command. You can see the cd writer device I have and you can use the dev=/dev/hdc as the device to write the files to. This works very well for me despite giving an error message about not really liking this method. But it does work. Long lines folded.

`--> sudo cdrecord -scanbus -dev=/dev/hdc
Cdrecord-Clone 2.01 (cpu-pc-linux-gnu) Copyright (C) 1995-2004 J�g Schilling
Note: This version is an unofficial (modified) version with DVD support
Note: and therefore may have bugs that are not present in the original.
Note: Please send bug reports or support requests to http://bugzilla.redhat.com/bugzilla
Note: The author of cdrecord should not be bothered with problems in this version.
scsidev: '/dev/hdc'
devname: '/dev/hdc'
scsibus: -2 target: -2 lun: -2
Linux sg driver version: 3.5.27
Using libscg version 'schily-0.8'.
cdrecord: Warning: using inofficial libscg transport code version (schily - Red
Hat-scsi-linux-sg.c-1.83-RH '@(#)scsi-linux-sg.c        1.83 04/05/20 Copyright
1997 J. Schilling').
scsibus1:
        1,0,0   100) 'HL-DT-ST' 'RW/DVD GCC-4522B' '1.02' Removable CD-ROM
        1,1,0   101) *
        1,2,0   102) *
        1,3,0   103) *
        1,4,0   104) *
        1,5,0   105) *
        1,6,0   106) *
        1,7,0   107) *

The command below will write the ISO image to a CDR and using your CD writer drive. I am doing it this way as I am using 2.6.14 and it has problems with detecting CD writer drives so I am doing it this way, it works very well this way too. Then you can type as root: mount /media/cdrecorder and check out your new CD to make sure that the files where copied across OK. I found that it is a bad idea to have files with spaces in the filename. Best to rename those files. My CD Writer drive is not SCSI so it is not detected as a SCSI drive. cdrecord -scanbus only finds my USB drive. That is why I am specifiying dev/hdc as the drive to use. Then it will know which drive to send the data to. I am using Kernel 2.6.18.2 now and this is still not fixed. But the output above from cdrecord shows how you can use the dev=/dev/hdc option for cdrecord to tell cdrecord which drive you have. I guess using this method is better than nothing. And my drive is detected by Xcdroast in Fedora Core 6. See here for a screenshot. The screenshot to the right shows how to enable the option to have relaxed iso9660 filenames to burn ISO's with many and varied files inside. You can type: cdrecord dev=/dev/hdc -v music.iso as root to burn a ISO image to a CDR.

Using the Xcdroast program to burn a bootable cd is much easier than some people would have you believe. I am assuming the program has detected your cd burning drive. Mine is a CDRW/DVD drive. Else you can set the device manually, e.g '/dev/hdc'. This is what worked for me. Setting it up in this program is easier than with something like Graveman or Nautilus CD Burner. Anyway, once you have setup the image directory to point to the path containing your wav files, you then select "Create CD/DVD" then "Write Tracks." This screenshot here Illustrates this. We are burning a Data CD in this example but we use exactly the same process to burn an ISO, except the ISO image is only one track.

 Track Selection. In this second screenshot, we are selecting tracks that will make up our CD. Just click on the tracks in the right hand pane and click 'Add', they will be added to the list to the right in the order that they will be burned to the CD, or you can just drag and drop the files into place. When you are finished arranging the tracks, click the 'Write Tracks' tab and select the options on this screen. Write Tracks. The only options we need to worry about are the options for multi-session and fixating our cd. Leave the 'Write as multi session' option unselected and make sure 'fixate cd' is checked as well as 'Enable protection from Buffer Underruns' is also selected. Select your disc type, e.g 80min and click the 'Write Tracks' button to burn the selected tracks to your cd.

If all went well a window will pop up showing the progress of your burn. Once the job is finished, the window will give you the option of closing the window or saving the progress report to a file. The disk will be ejected once the job is complete. And once you have exited the Xcdroast program you may re-insert your cd and mount it to test your disc. Go to an Xterm and su to root and then type mount /dev/hdc /mnt/cdrom to mount your disc. Then type cd /mnt/cdrom to go to your new cd and browse the files to ensure the disc is fine. And just type eject to eject the disc.

To burn an ISO image to a new blank CD, you use the same procedure as outlined above. The ISO image will appear in the right hand pane and you click the image file and click 'add' to add the ISO image to the track listing. Just as we did with the wav audio tracks. Then we go to 'Write Tracks' and follow the above procedure to write the image to the cd. I have used this procedure to burn the Smoothwall ISO to a cdrw disc and it has worked flawlessly. Some people on the forums will advocate using cdrecord, but in some cases it will not detect the drive, so you will need to specify the actual device e.g, dev=/dev/hdc since it seems to work perfectly with just about any CD Writing device. Using the Graphical User Interface makes the job easier and more exact. But if you do not have Xcdroast, then you can use the commandline utilities by hand to do the job. As I have outlined above in the command line section, it is easy to do. And very fast too.

Now that your CDR is complete, re-insert the CD, reboot, and your new CD should boot!. There, you have burned a bootable ISO image. If you have downloaded multiple images, just repeat the process for all of the ISO images in turn to create all the CDs you require. A note for those who are running Mandrake Linux 10.0, the first CD has a boot.iso file on the installation CD which is about 7.98MB. If you burn this file to a blank CD you will get a bootable rescue cd which is more useful than a 3.5 floppy disk that is for sure. I am sure that other distros have this feature as well in one form or another, it is much more reliable than an unreliable boot/rescue floppy and would have more features crammed into a larger ISO image. Although sometimes you can use the installation CD/DVD itself as a rescue disk. Especially Red Hat Linux. Or SUSE Linux 10.0.

If you are wanting to burn a Symantec Ghost image to CD, e.g to backup your Windows partition, then you could use Linux to burn the CD. You will need to copy the ghost image onto a separate partition and then use a bootable ghost disk to load up the ghost program and restore the ghost image. If you make a ghost image of the partition this is better than making an image of just the data. You would not need any special options to write the image to CD, just copy it straight to the CD, so you will have a backup. Then as I said before, you can just copy it back to a separate partition and restore the image.

I have done this when I was running Windows '98 and it worked very well. Obviously you cannot have the ghost image on the same partition you are restoring to, but I have had not much luck restoring the image from the CD unless you made it a bootable DOS CD and included ghost on the disk as well. I have seen restore CD's for Windows XP that used this setup and very well too. If you made a freedos CD with ghost and your image, you could have a backup of your OS on a CD or DVD.